Studio-in-the-Cloud

Job submission is the initial step where users provide all the necessary data and instructions for the render farm to begin processing. This process involves several sub-steps to ensure that the job is correctly configured and ready for distribution.

Job Submission Breakdown

1. User Interface Interaction
   • Users interact with the render farm management software via a user interface (UI), which could be a web portal, a desktop application, or a command-line interface (CLI).
2. Input of Job Details
   • Scene File: The user selects the main scene file to be rendered (e.g., a .mb file for Maya, .blend for Blender, etc.).
   • Assets: Users specify additional assets required for rendering (textures, models, shaders, etc.).
   • Render Settings: Users configure settings such as resolution, frame rate, number of frames, quality settings, etc.
3. Segmentation Strategy Selection
   • Users choose how the job should be segmented:
     • Frame-Based: For animations.
     • Tile-Based: For high-resolution still images.
     • Layer-Based: For scenes with multiple render passes.
     • Custom Segmentation: For specific custom requirements.
4. Resource Allocation Preferences
   • Users specify preferences for resource allocation:
     • Compute Instance Type: Standard, high-performance, or GPU instances.
     • Number of Instances: Number of compute nodes to use.
     • Priority Level: The priority of the job (high, medium, low).
5. Job Metadata
   • Users provide metadata for the job for tracking and organization purposes:
     • Job Name: A descriptive name for the job.
     • Job Description: Additional details about the job.
     • Tags: Keywords for categorizing the job.
6. Deadline and Scheduling
   • Users can specify deadlines and scheduling options:
     • Deadline: The date and time by which the job must be completed.
     • Start Time: When the job should start if it should be delayed.
     • Scheduling Preferences: Preferences for scheduling, such as running during off-peak hours.
7. Dependencies and References
   • Users specify any dependencies or references needed:
     • Dependency Jobs: Other jobs that must be completed before this job can start.
     • Reference Files: Files that need to be referenced but not necessarily rendered.
8. Preview and Validation
   • Before submission, users can preview and validate their job configurations:
     • Preview: A preview of the scene or frames to ensure correctness.
     • Validation: Automated checks to ensure all required files and settings are correct and available.
9. Submission
   • Once all details are correctly filled out, users submit the job:
     • Job Submission: The job is submitted to the render farm management software for processing.
10. Job Queuing
    • The submitted job is placed in a job queue:
      • Queue Position: The job is positioned in the queue based on its priority and scheduling settings.

Example Job Submission Workflow

Step 1: User Interface Interaction

• Action: User logs into the render farm web portal.

Step 2: Input of Job Details

• Scene File: User uploads scene_file.mb.
• Assets: User uploads textures, models, and shaders.
• Render Settings: User sets resolution to 1920x1080, frame rate to 30 FPS, and frame range from 1 to 300.

Step 3: Segmentation Strategy Selection

• Selection: User chooses “Frame-Based” segmentation.

Step 4: Resource Allocation Preferences

• Instance Type: User selects high-performance instances.
• Number of Instances: User requests 20 instances.
• Priority Level: User sets the job to high priority.

Step 5: Job Metadata

• Job Name: User names the job “Project_X_Animation”.
• Job Description: User describes the job as “Final render of Project X animation sequence”.
• Tags: User tags the job with “ProjectX, Animation, FinalRender”.

Step 6: Deadline and Scheduling

• Deadline: User sets the deadline to 2024-07-15 18:00.
• Start Time: User sets the start time to 2024-07-10 00:00.
• Scheduling Preferences: User opts to run the job during off-peak hours.

Step 7: Dependencies and References

• Dependency Jobs: User specifies that “Project_X_Lighting” job must be completed first.
• Reference Files: User uploads a reference HDRI file for lighting.

Step 8: Preview and Validation

• Preview: User previews the first and last frame of the animation.
• Validation: System checks for missing assets and verifies render settings.

Step 9: Submission

• Action: User clicks “Submit Job”.

Step 10: Job Queuing

• Queue Position: Job is added to the queue and assigned a high priority position.

Visual Representation

Here’s a flow diagram representation of the job submission process:

[User Interface Interaction]
           |
           v
   [Input of Job Details]
           |
           v
[Segmentation Strategy Selection]
           |
           v
[Resource Allocation Preferences]
           |
           v
       [Job Metadata]
           |
           v
  [Deadline and Scheduling]
           |
           v
[Dependencies and References]
           |
           v
  [Preview and Validation]
           |
           v
       [Submission]
           |
           v
     [Job Queuing]
           |
           v
       [End of Submission Process]